UPOP UP REFERENCEPRM-DATA MENUS AREA╒GENERAL CONTROLS≡	TERMINAL AREA OPTIONS√PORT SELECT/CONFIGURE²&≤UART LINE CONTROL≡3(BAUD SELECT:üDEFAULT VIDEO EMULATIONÖ>z$KEY TRANSLATION SEQUENCE FILE (.KTS)D╤KEYBOARD MACRO ASSIGNMENTSΣFò	DIRECTORIES IN USE MENUyP>	AUTO DOWNLOAD SEQUENCE TRIGGERS╖YâAUTO LOG ON TRIGGER SEQUENCE:i┐INTERACTIVE EMSI DATA∙l╟	RECEIVER PROTOCOLS└vsSENDER PROTOCOLS3É¬TELEPHONE DIRECTORY AREA▌ól
FON.RECORD EDIT MENUI░╒INTERNAL FILE LISTER╔	EMSI DATA"▐ßPOINT MAIL FUNCTIONSπêMOUSEïτj
AceComm's Keyboard is re definable. Each key press can be re
assigned a different function, or set of functions. To
accomplish keyboard re definition, AceComm uses descriptive
text symbols called MACROS. MACROS are enclosed inside of
angled brackets.

The Popup Reference displays each key press that has been
assigned to a MACRO, or MACROS.
The key press is displayed to the left, with it's MACRO
assignment to the right. The example below shows the MACRO for
AceComm's configurations area is assigned to ALT-P.

     ALT-P <PrmDataMenus_>


The Pop Up Reference menu displays the current .KBD file's
MACRO(S) assignments.  A .KBD file contains a copy of all
key-press MACRO(S) assignments.  AceComm supports unlimited .KBD
files.  Each key press combination can be assigned a MACRO(S).
AceComm allows the user to re define the keyboard functions if so
desired.  AceComm provides a rich set of MACRO functions for all
of AceComm's internal functions.  A complete MACRO list with
descriptions is contained in the MACRO.DOC file.

"Print_template" allows you to print a list of keys that have
MACRO assignments.  The default filename is "PRN".  You may find
it handy to print to a FILE, (key.prn) or similar, this way you
can format the TEMPLATE, for a more custom print job.


o MACRO for this menu is: <PrmDataMenus_>
  (default assignment is to both ALT O & ALT P)

o All PRM-data changes are auto-saved when Auto-Save flag is
  "ON"

o Each sub-menu contains context sensitive HELP

Virtually any data contained inside the ACE.PRM file is
accessible and configurational from the PRM-data area.  Above is
the menu you will see after pressing key-combo <PrmDataMenus_> is
assigned to from the TERMINAL area.

Notice the second to bottom line of text in the menu says
"AutoSave ON".  AutoSave can be toggled On/Off from inside the
"General Controls" menu.  When ON, changes made from inside the
PRM-data menus are saved to ACE.PRM automatically.  If AutoSave
has been toggled OFF, the "AutoSave ON" is replaced on the menu
with "Save Changes" and this menu item must be selected for
changes to be kept past exiting AceComm.  Note: If you toggle
"AutoSave" to Off, you will select the "Save Changes" option
before exiting AceComm, if you want the toggled option to remain
toggled.  Otherwise, AceComm will be back to "AutoSave" when
re-started.

Notice the TEXT LINE directly below the menu.  The line is
AceComm's context sensitive help display for that current
"highlighted" line.


o The controls are enable/disable flags, some of which can
  also contain a value for timers.

o Controls in this menu are more general, Terminal Area Options
  menu contains a similar menu with toggles that affect the
  Terminal Area only.

All controls are a series of flags which tell AceComm when to use
some of the features, and when not to.  Flags with the ON/OFF
status are toggles, and will be toggled here in this menu.
Notice the "Screen Saver" flag description contains the number 3,
rather than an ON/OFF.  Selecting Screen Saver mode 0 = OFF.
Screen Saver can be set from 0 - 10.  Values above 0 are minutes
without a key press to AceComm blanking the screen.  Screen is
restored with a key press.  Un-blank-key-press is valid.  Use ALT
alone for non-destructive key press to un-blank the screen.

- Allow enhanced keyboard detection        Yes
  AceComm will detect and use enhanced BIOS keyboard functions.
  Some systems may not fully support this mode properly. This
  flag allows locking out AceComm's use of enhanced BIOS
  keyboard functions.

- Allow mouse detection                    Yes
  Setting this to "NO" will cause AceComm to act as if a mouse
  is non existent, the mouse driver is never initialized, no
  mouse menu is presented in the Terminal Area.


- Mouse horizontal sensitivity             6
  Mouse sensitivity is already set in the mouse driver. This
  value is internal to AceComm only

- Mouse vertical sensitivity               4
  Mouse sensitivity is already set in the mouse driver. This
  value is internal to AceComm only

- Inter Byte Delay                         Off
  Add 55 millisecond delay between modem command characters.
  Also adds an extra second between re dials, before MDM_INIT
  etc.

- Auto Save Changes                        On
  When "ON" AceComm will save PRM-data changes to the ACE.PRM
  file.  When "OFF" the prompt inside the main PRM-data menu must
  be selected for PRM-data changes to be recorded to file.  This
  pertains to actual PRM-data below the menu system data.  Menu
  area attributes are ALWAYS SAVED, with exception to "Mass Menu
  Area" changes, these must be affected using the appropriate
  selection from inside "Mass Menu".

- Snow (vertical retrace) checking         Off
  AceComm uses direct video buffer writes for all it display
  areas.  Most areas will be able to handle SNOW CHECKING
  properly before making screen updates.

- Swap for <RunProgram>                    On
  XMS, EMS, DISK swapping for the AceComm executable will take
  place when this flag is set "ON".  When SWAPPING is active,
  AceComm 's SIO is deactivated while <RunProgram> MACRO is
  active.
  Notes: AceComm is currently using Ralf Brown's SWAP functions
 for the SWAP service.  SWAP is the only code inside
 AceComm executable that is not written entirely by MGP
 Programming Services.  SWAP has proven to be the most
 dependable code of this type that has been tested in our
 executable files.  MGP Programming Services would like
 to thank Ralf Brown for permission to use his SWAP code
 in our products.

- Swap for <CommandShell_>              On
  XMS, EMS, DISK swapping for the AceComm executable will take
  place when this flag is set "ON".  When SWAPPING is active,
  AceComm 's SIO is deactivated while <CommandShell_> MACRO is
  active.
  Notes: The Notes for <RunProgram> apply to this MACRO

- Screen Saver timeout value (minutes)     3
  Screen Blanking service.

- Keep Log file                            On
  Toggle AceComm use logging ON/OFF.

- Modem Response Timeout when dialing      48
  Master timeout when dialing.  Overrides your modem's own S7
  register.
  Notes: It is best to set this value several seconds above your
 modem's S7 register.

- Seconds between re dials                 1
  AceComm will pause this many seconds between receiving a modem
  response string, or timing out, and sending the next dial
  string to the modem.  The variable can be toggled from 0
  seconds to 12 seconds.

- All Sounds Override Switch <> Sounds are Off
  Toggle, enable/disable all sounds. Master override.

- Ring BELL on Dial/Connect                1
  Seconds to ring BELL on successful detection of either DCD or a
  connect message response from the modem.


o The controls are enable/disable flags, some of which can
  also contain a value for timers.


- Status line                              On
  Toggle AceComm 's STATUS LINE On/Off
  Notes: AutoScrGen(tm) will assert the STATUS LINE, and restore
 it on when through.  The RunScript function will do the
 same.

- Mouse Menu                              Yes
  Display 1 line mouse menu on Terminal Area screen

- Auto Download                            On
  Activate/deactivate AutoD trigger sequences.  Associated AutoM
  MACROS are activated/deactivated as well.

- File Resume                              On
  For internal Zmodem. Resume "ON" existing files, data is
  appended to the file, "OFF", the file is created new, any
  existing file of the same name is over written.

- Ring bell after internal protocol        20
  Internal protocols will sound an alarm before returning to
  Terminal Area.  A value of "0" disables any sound after
  internal protocols.  A value of "1" plays a Victory tune.
  Values from 2-30 become seconds to sound the internal bell.
  See also <RingBell> 5 MACRO

- Screen Saver if Data Carrier Detect      No
  Screen Blanking service disabled during modem status DCD bit
  detected to be ASSERTED.

- BackBuf Lines (100=16k (80 wide Color)) 400
  Setting the field to "0" turns the buffer "OFF".

- Terminal Area screen color (TTY mode)    7
  This setting allows changing the Terminal Screen color that is
  initially active when AceComm is started.  The color will
  remain constant through TTY video emulation.

- Drop DTR when quitting AceComm            No
  AceComm will or will not drop DTR when the <EndACECOMM> MACRO
  is run.  Most modems will by default, drop carrier along with a
  drop in DTR.  DTR is a bit in the modem control register of the
  UART.  Setting this to "YES" will cause AceComm to drop DTR
  when ever <EndACECOMM> MACRO is executed.

- Log modem response while off line        No
  AceComm can log modem response strings that come in.  This flag
  will tells AceComm if it should log the responses.  This is for
  off line only.  This flag is most use full when you want to
  know when your phone rings, AceComm will TIME STAMP PRM-data
  Area MDM_RESPONSE_RING responses strings.  Many modem ROMS are
  now featuring caller ID.  Modems that have caller ID ability
  will be able to present to the terminal screen the caller ID
  info, if available.  This information will also be logged along
  with the TIME STAMPED "RING".

- Strip high bit from incoming             Off
  "Off" data received from the modem is un altered. "ON" data
  is stripped of any bits above the decimal value 128.

- Default Video Emulation                  Av/An
  This selection brings up another menu.  The menu displays the
  available video terminal emulation modes.  Along with their
  associated KTS files.  This setting affects the default video
  terminal setting for AceComm.  Individual FON RECORDS contain
  their own video terminal settings.



o Install option, AceComm will close the active port and install
  it's SIO on the port selected.  MDM_INIT string is sent to
  modem.

o Edit option, you will be prompted for port address and IRQ.
  Address is a HEX number.  Entering a decimal value will fail.

Port numbers are merely symbolic for identification.  Port
addresses and the Interrupt ReQuest line for the address is
configurational.

  * Rbuf/Tbuf are the buffer size used for serial I/O.  Normally
    there won't be any advantage to raising the TBuf size.  RBuf
    size will be adequate at about 1024 bytes for all normal
    use.  The larger value (default) will allow storage of
    incoming during Back buffer, Tagger etc.  RBuf range is from
    1k to 32k, TBuf 128 bytes to 32k.  The Zmodem sending unit's
    window size is equal to TBuf size.  Window size is not
    data-frame size.  Window size means "how much data to we let
    build up into the TX buffer at any one time.  RBuf/TBuf can
    be changed at any time, on line or not.  It is recommended
    that the HOST be still when re-sizing RBuf/TBuf.  RBuf/TBuf
    changes take immediate affect.

  * FIFO trigger is the number of bytes buffered before a First
    In First Out UART chip will alert the CPU by way of
    interrupt.  FIFO UART operation is automatically enabled when
    a FIFO UART is detected.  AceComm always checks for FIFO UART
    presence whenever installing onto a PORT.  FIFO trigger level
    changes take immediate affect.  Trigger level of "1"
    affectively disables the FIFO affect.

  * Chain IRQ "share IRQ" will cause AceComm 's SIO ISR to pass
    on the interrupt request to the Interrupt Service Routine
    which was present on the IRQ when AceComm installed onto the
    port.  The Chain IRQ toggle takes immediate affect.  IRQ
    sharing is not supported by -most- I/O cards.  Use the option
    at your own risk.  Notes: IRQ sharing may appear to work
    properly on your setup, even though your hardware was not
    designed for IRQ sharing to take place.  There are some good
    technical points to be made for degradation that may be
    caused in the I/O cards, when forced to drive the IRQ line
    HIGH, while another is doing it's best to pull the same IRQ
    line LOW.

  * TX is a flag that tells AceComm to use interrupt driven
    output.  Interrupt driven input is always on.  The TX toggle
    takes immediate affect.  If you FAST computer/modem setup is
    capable of overwhelming the other end when sending data,
    toggling TX "OFF" may improve the situation.

  * CTS/RTS hardware handshaking / FLOW control
    Hardware handshaking may normally be left ON (default). High
    speed modems using fast data rates and typically locked port
    rates will require software to use FLOW control.

  * XON/XOFF software handshaking / FLOW control
    Many HOST software will recognize XON/XOFF FLOW control.
    You may need software handshaking enabled for proper FLOW
    control while performing ascii uploads.

      Notes: AceComm uses FLOW control flags (above) primarily to
     detect when not to send data to the modem.

     AceComm will automatically use both forms of FLOW
     control when it detects the receive buffer getting
     full.

The UART's line control register can be set for several different
data arrangements.  Most common being 8 data bits, no parity bit,
1 stop bit.  Most BBS systems will use the 8N1 configuration.
The UART uses the line control information when assembling
incoming bits into a byte.  Setting this information from the
PRM-data area, the format is stored in the default settings for
AceComm to use.  When you look at the FON directory records you
will see that each record stores it's personal line control
setting to be used when dialing the record.  Data format is saved
with each individual record in the record's .FON file.  When
using AceComm in HOST mode the default setting will be used.
AceComm retains the default line control register setting in the
ACE.PRM file.  FON record line control settings are stored in
their respective .FON files.

BAUD rate is also something that will normally be attached to a
FON record and used when dialing the record.  This is of more
concern to users of modems that do not allow LOCKING the port.

LOCK BAUD is almost always available as an option when using a
modem that can support CONNECT rates above 2400 baud.  When using
the LOCK BAUD option, AceComm will leave the port speed alone
when dialing.  The modem handles speed translation between
'connect' and 'computer'.  LOCK BAUD ON is generally preferable
with modems that support it.  The status displays will reflect
'L' appended to the baud rate when LOCK BAUD is set ON.  NOTE:
the 'L' is not appended in the Line Control Window's display
above.

   "Selecting your highest port speed when LOCKing the port"
- Modem Speed can be set to highest baud your modem/computer will
   handle including locked ports.  Locking the port at 57600 with
   a high speed modem causes the UART to assemble a character off
   the bit stream VERY quickly.  If you experience serial input
   errors with HIGH locked rates, drop down to 38400 or even
   19200.  The lower rate will cause the UART to make characters
   available at a reduced speed.  For instance a 12 MHZ AT will
   probably experience data overruns using a locked port above
   38400 when down loading TEXT files with ZMODEM.  A common
   miss-conception is when CRC errors occur with HIGH LOCKED PORT
   rates, that it is the UART unable to keep up.  This is simply
   not true.  The UART/modem combo is capable of out running the
   computer/software combo.  When using a TASK switcher such as
   WINDOWS or DESQVIEW, a lower PORT RATE such as 19200 may very
   well be needed for efficient data transfers.  The idea is to
   set the port to a speed that the computer/software combo is
   capable of responding to quickly enough.

o Video Terminal emulation is built into AceComm

o Associated KTS file is the Keyboard Translation Sequence file
  that will be loaded for the given Video Type.

o Keyboard Terminal emulation is defined inside of *.KTS files
  AceComm includes a separate utility KTS.EXE which allows the
  user to define KTS files for any Keyboard Terminal emulation
  desired.

AceComm emulates the selected VIDEO type.  "Associated KTS file"
is the .KTS file you want to use with the VIDEO selection.  Each
time AceComm activates a VIDEO type, the associated KTS file is
loaded and becomes active on the keyboard.  KTS keyboard
definitions override MACRO assignments.

KTS (Key Translation Sequence) files contain assignments for
a sequence of characters to a key press. When a key is pressed
from inside TERMINAL area, AceComm first checks to see if the
key press has been defined in the current KTS data. If so,
AceComm sends the assigned sequence of characters to the modem.
The utility KTS.EXE (included) can be used to create new and or
custom KTS files. See the included .ASC examples for defining
and creating KTS files. Using KTS.EXE, the keyboard can be
deigned to emulate any possible combination of characters
available to the system.
Key press assignments defined in the KTS data area are given
top priority, and thus take presides over MACROS assigned to
the same key.



KTS files contain a sequence of bytes to be sent to the modem
when a particular key press is made. AceComm emulates a video
type independently from the keyboard emulation. KTS files may
be edited to emulate any combination imaginable. KTS files may
be created and assigned to a video type using the "Associate"
option above.

AceComm comes with ready made KTS files.

   Notes: .KTS files are compiled from .ASC files.  .ASC files
  may be created, maintained, customized with a TEXT
  EDITOR in ASCII TEXT mode.  The utility KTS.EXE is
  provided for compiling .ASC files into .BIN files.
  Rename the .BIN file with .KTS and copy the .KTS file
  into the directory pointed to in PRM-data for ".KTS".

o Each of the above key sets is available for assignment to a
  MACRO or MACRO stack.  The MACROS provide a wide range of
  services.  All of AceComm's functionality is available with
  MACROS.

o The "SHIFT-Fn" key-set is used by TAGGER to store TAGGED ITEMS

--Write--
  Prompts for a filename, and writes the current keyboard to a
  new KBD file, or updates an existing KBD file of the same name.
  When you choose "Write" the following occurs:
    AceComm  prompts  for  "filename"
    "filename"  is  forced a ".KBD"  extension
    "filename" is written in the same directory as ACE.PRM
    resides
    AceComm writes the contents of "Key MACRO Assignments" menu
    to the file
    AceComm re-reads the original KBD file.

  In short:
  - All changes, once written to a KBD file with "Write", pertain
    to the KBD file written to.
  - Making changes and not "Writing" them, will be saved to the
    current KBD file at program end.

To further explain, all changes made in this menu area to the
keyboard definitions, apply to the current KBD file.  If you exit
the menu area, without choosing "Write", and say "ACE_DEF.KBD" is
active, the changes will be stored to "ACE_DEF.KBD" when you
leave the PRM-data area.  If you choose "Write" from the above
menu, then the changes are stored to a new or existing KBD file,
and do not affect the current keyboard, as AceComm re-loads the
current KBD file after a "Write".  Unless you "Write" to the
current KBD file, which is un necessary, because AceComm will
update it automatically anyway.

"SHIFT-Fn" is the key-set the TAGGER function assigns TAGGED
ITEMS to.
When you tag a word or line from the screen, the tagged item
becomes associated with the first available SHIFT-Fn key by way
of the <SEND_SendStr> MACRO.

   ╔═════════ACE.PRM Data  Edit-Menus═══════╗
   ║ General Controls                       ║
   ║ Serial Port Setup                      ║
   ║╔═KeyBoard MACRO Assignments═══╗        ║
╔═ F# Keys ════════════════════════════════════════════════════
║  1<SendStr>Michael Phelps^M
║  2<SendStr>[FON_REC_PWD]^M
║  3<SendStr>Phoenix, AZ
║  4<SendStr>[PASSWORD]^M
║  5
║  6
║  7<SendAscii> %P
║  8
║  9
║ 10<SendStr>password^M
║11
║ 12<SendFile> message.txt
╚═══ Edit  Zap  Quit ══════════════════════════════════════════

- Edit
  Allows editing the MACRO assignment.

- Zap
  Clears field (Zaps) the MACRO assignment.

- .FON
  Where AceComm expects .FON files to be.

- .CAP
  Where AceComm will create and  or  re-open  CAPTURE  files.   A
  CAPTURE  file  is a means for "capturing" all port I/O to DISK.
  When you open a capture file, AceComm records  everything  that
  comes  into  the  serial  port,  exactly  as  it  comes in.  No
  filtering, no translation of  any  kind.(1)  AceComm  does  not
  overwrite  CAPTURE  files.  You have the option of renaming the
  file, or AceComm will  append  new  data  to  the  end  of  the
  file(2).

- .SCR
  Where  AceComm  will  create  and  or look for .SCR files.  The
  MACRO <RunScript_> lists this directory.

- .KTS
  Where AceComm expects to find it's KTS files.  It's ok to store
  your .ASC files in this directory.

- Downloads
  This is the directory that AceComm 's internal  protocols  will
  receive  into.   AceComm  will  also  list  this directory when
  building upload LISTFILES.

- Nodelist
  When you select the FileRequest option, AceComm expects to find
  either (a) a valid RAW FIDO  NODELIST  and  NLIST.IDX  file(3).
  or (b) a .NOD file(4)

- .REQ/.MLF
  Mailer  activities.

  .REQ files are used when doing File Requests.  When you ask
  AceComm to make a File Request, the filename is created using
  the NET/NODE number in ascii hex, and the file extensions is
  ".REQ".

  .MLF files (Mail List File) are used when you want to File
  Attach to a NET/NODE.  File Attach may be any file(s), and will
  also serve as a means for point mail operators to send their
  mail bundle to the HOST.

(1)  ANSI.EXE is a provided utility that can filter VIDEO CONTROL
     SEQUENCES from DISK files.

(2) If you have edited a CAPTURE file, or by other means used any
     utility that added the 26d character to  the  file,  AceComm
     will  not  overwrite  the  END  OF FILE character.  This may
     result in some editors not recognizing new data that follows
     the 26d character.  There exists utilities that  can  filter
     this and other characters from TEXT files.

(3)  NLIST.IDX  is  a  file  created  using  the  AceComm utility
     IDX.EXE.  IDX.EXE will create a small  index  into  the  RAW
     FIDO NODELIST file, for all ZONE:NET pairs.

(4)  .NOD  files  are  FBL  output for a NET.  FBL.EXE is another
     AceComm utility.


o The last byte in a Trigger Sequence is the sequence scan
  trigger byte

o The last byte in a Trigger Sequence should end in an un
  common character (as designed above)

o EMSI_REQ detection can allow swift access to a BBS when
  mailer software answers the phone

o EMSI_IRQ is sent by BBS software to tell the caller it can do
  Interactive EMSI data handshaking

  The above defaults have been working very well for the
  protocols associated.


--Trigger Sequence--
  A trigger sequence is a character string that is used by a
  remote HOST, protocol etc. as an attempt to engage some
  action from the other end.

--Trigger Character--
  AceComm scans back thru it's receive buffer for a trigger
  sequence with each occurrence of the "last byte of the
  sequence".  This means that AceComm will scan for the string
  each time it sees the trigger byte arrive from the modem.  For
  this reason a trigger sequence will end in a non-common byte.
  While 'rz^M' (^M being <CR>, 13 decimal) would be a valid
  trigger sequence, we don't want AceComm to search on every
  carriage return character that comes in.  Look at Bimodem's
  trigger sequence, we don't want to end the sequence with a <SP>
  character (^' is the control code for SPACE CHARACTER 32
  decimal).

  Characters 32(Space) and below need be escape encoded with
  the '^' ^A becomes 1, ^B 2, ^C 3, ^M <CR>, ^` 32 <SP> etc.


      **EMSI_REQA77E
  Most FIDONET mailer software will send an EMSI_REQ string to a
  caller.  This string is an attempt to determine the caller
  type.  AceComm's <SendEMSI_CLI> MACRO tells the mailer this is
  a human caller, by passing the common "Press ESC to enter BBS"
  prompt.  DBridge mailer software is in complete and won't
  recognize this advanced EMSI handshaking.  All other mailer
  software does.

      **EMSI_IRQ8E08
  IEMSI capable BBS systems will send an EMSI_IRQ string to a
  caller.  Detection of EMSI_IRQ is responded to with IEMSI data
  handshaking.  AceComm's <SendEMSI_ICI> MACRO handles IEMSI log
  on.  (see PRM-data IEMSI Setup menu)

--Responding MACRO Stack--
  The MACRO defined to the right of each trigger sequence will be
  used when a sequence has been detected.  This allows AceComm to
  be configured with auto download detection for up to 10
  protocols.  MACRO STACKING is valid with AutoM MACROS.

  The sending of a carriage return as the last macro is use full
  for moving the BBS display upon return from the external
  protocol.  AceComm completely disables the serial port before
  calling any external programs.

--PreAutoM MACRO--
  The "PreAutoM" MACRO, if defined, will be processed prior to
  the AutoM MACRO about to be processed.  This allows for some
  extra maneuvering to be done which might otherwise be common to
  all AutoM MACROS anyway.  For instance the practice of changing
  to your "FILES" directory will insure that downloads are
  received into the "FILES" directory, even with protocols that
  do not allow file redirection.

  Notes: If you use PreAutoM MACRO for changing directories,
 remember that protocols such as BIMODEM which you may be
 up loading with at the same time, will need full path
 names to files they are to send.  Also protocols or what
 have you that use PRM, CFG etc.  files need know where
 to find these control files.

--PostAutoM MACRO--
  The "PostAutoM" MACRO, if defined will be processed immediately
  following the AutoM MACRO.  Again this is some extra MACRO
  processing power for those common to all AutoM MACRO jobs.

To Disable Auto Download Sequence Triggers
  Located in the "Terminal Area Options" is a over ride flag with
  which Auto downloads may be completely disabled.  This flag
  affects all Trigger Sequence/AutoM MACROS pairs defined.

  Auto Download                            On    <=-ENABLE
  Auto Download                            Off   <=-DISABLE

╔═Auto Log On Trigger Sequence══════════════════════════════════
║═Trigger Sequence -- Responding MACRO STACK════════════════════
║ is^`your^`name:     <SendStr>[USER_NAME]^M~Y^M~[FON_REC_PWD]^M
║ is^`your^`name:     <SendStr>[USER_NAME]^M^M~[FON_REC_PWD]^M^M
║Host^`Name:        <SendStr>CIS^M~75120,3306^M~[FON_REC_PWD]^M
║ first^`name^`?      <SendStr>[USER_NAME]^MY^M[FON_REC_PWD]^M
║
║
║
║
║
║
╚═══ Select  Edit  Null_Selection  Quit  Help ┤<>v^├════════════

o Each Fon.Record can be assigned to one of the Auto Log on
  definitions available from a menu when selecting this option.

o AceComm will respond to a trigger sequence by processing the
   MACRO stack.

o Log on trigger sequence scanning is available immediately after
  connect, and until the sequence has been found.

o  When a log on sequence has been processed, AceComm stops
   scanning for the log on sequence for the remainder of the
   on line session.


o Interactive Electronic Mail Standard Identification (IEMSI)

o IEMSI is an auto log on interface designed to present caller
  information to the HOST quickly and automatically. Few BBS
  systems currently support IEMSI. RA supports IEMSI log on.

o Interactive EMSI log on function is called with the
  <SendEMSI_ICI> MACRO function

o Data defined here will be used by the <SendEMSI_ICI> MACRO
  function

o All IEMSI data need not be defined. The BBS system will
prompt the user for any invalid or missing information.

- User Name and Alias
  Enter your name as you want it to appear to a BBS system.
  There is also a  PRM-data  MACRO  [USER_NAME]  that  uses  this
  field.
  There is also a PRM-data MACRO [ALIAS] that uses this field.

- Location
  City, State, Country
  There is also a PRM-data MACRO [LOCATION] that uses this field.

- Data # and Voice #
  If  you have no Data #, leave the field blank.  There is also a
  PRM-data MACRO [DATA_PNUM] that uses this field.
  There is also a  PRM-data  MACRO  [DATA_PNUM]  that  uses  this
  field.

- Password
  This is a default password, any FON.RECORD.PASSWORD always will
  override this IEMSI PASSWORD.
  There is also a PRM-data MACRO [PASSWORD] that uses this field.

- Birthdate (currently unused)

- CRT def    (current session only)
  Consists  of  four sub-fields separated by commas, from left to
  right:TERMINAL EMULATION,ROWS,COLUMNS,NULS

       Example: AVT0,24,80,0

  TERMINAL EMULATION
  Video type
      AVT0        (AVATAR/ANSI)
      ANSI
      VT100
      TTY
  ROWS
 Video rows for current session only
  COLUMNS
 Video columns for current session only
  NULS
 00h character required after line feeds.   AceComm  uses
 should leave this field set to ZERO (0)

- Protocols
  AceComm internal protocols support ZMO,ZAP fields.
  ZMO is normal zmodem
  ZAP is zmodem with up to 8k data frames.

- Capability    (current session only)

  CHT       Can do full screen on line conversation (CHAT)
  TAB       Can handle TAB (ASCII 09h) characters
  AceComm supports TAB
  ASCII8    Can handle 8-bit IBM PC ASCII characters

- Requests      (current session only)

  NEWS      Show bulletins, announcements, etc.
  MAIL      Check for new mail
  FILE      Check for new files
  HOT       Hot keys "ON"
  CLR       Screen clearing
  HUSH      Do not disturb
  MORE      Page pausing, often referred to as "More"
  FSED      Full screen editor

AceComm  contains  internal Xmodem, Xmodem 1k, Ymodem, Ymodem 1k,
Ymodem G, Zmodem, and a Zmodem variant ZedZap (8k).

--Internal Batch Capable--
  Batch protocols receive the incoming filenames as part of the
  file data sent from the sender.  AceComm will append filenames
  received from the remote sender to the directory path contained
  in the PRM-data area under "FILES".

--Internal Single File--
  Single file protocols require a filename be given locally, by
  the user.  The user is prompted for a filename between the menu
  selection and calling the internal protocol function.

--External Menu--
  "Externals" are defined as menu selectable executable that will
   become arguments to the <RunProgram> MACRO.

   You may find it simpler to assign external protocols to a "Hot
   Key" from inside PRM-data Key Definition menu.  This menu is
   provided for those who want a "menu driven" affect.

--Auto Engaging Menu--
  AutoDnlds are protocols whose sending units begin by sending a
  documented sequence of characters.  AceComm allows up to 10
  separate sequences be defined, and associates each sequence
  with a MACRO STACK.  the MACRO STACK can be setup to call the
  external protocol associated with the sequence.  "AutoDnLds" is
  documented in more detail above.  Shown below is a snippet
  reminder display.

  ╔═ AutoDnLd Trigger Sequences ═════════════════════════════════
  ║ rz^M**^X            <RecvZmo>
  ║ HS*^B               <RunProgram>hslink -P1 <SendStr>^M
  ║ ^`^H^`^H^`^H^`^H    <RunProgram>bimodem /C \ace <SendStr>^M
  ║ MPt^`^V^H           <RunProgram>MPT R <SendStr> ^M
  ║ at^`is^`your^`name: <SendStr>Michael Phelps^M~^M~PASS^M
  See "AutoDnLd Trigger Sequence" menu for more information.

--Recv Mail / File Request--
  "FileRequest" is a point mail function.
  Selecting File Request function will bring up the menu below
  if the PRM-data directory field for NODELIST points to either
    - FIDONET NODELIST and compiled NLIST.IDX file
    - FBL.EXE output .NOD file
  FBL output .NOD file is used in the example below.

 ╔═══════════════════════════════════════╗
 ║           1:114/12                   ║
 ║ Format =>  ZONE:NET/NODE              ║
 ╚═══════════════════════════════════════╝
 This menu prompts the user for a ZONE:BET/NODE number of the
 system we want to call. Having entered the above "1:114/12"
 the menu below is presented.

 ╔═1:114/12══════════════════════════════╗
 ╔═D:\ACE\fon\══════════════════════════╗║
 ║  1_105.NOD    19595   05/12/93 10:09 ║║
 ║ 1_114.NOD    11220   05/12/93 10:09 ║╝
O║  1_125.NOD    7886    05/12/93 10:09 ║
 ║  1_282.NOD    7623    05/12/93 10:09 ║
O║  1_382.NOD    10291   05/12/93 10:09 ║
 ╚═│Grab│ Quit ┤<>v^├═══════════════════╝
 This menu lists FBL output .NOD files found in the directory
 field NODELIST.  FBL produces these files and names them
 according to their ZONE_NET number.  We want to select the file
 1_114.NOD because 1_114.NOD is an extracted listing of all NET
 114 zone 1, from the FIDONET NODELIST.  Selecting the 1_114.NOD
 file produces the following menu.

 ╔═1:114/12══════════════════════════════╗
 ║╔═1:114/12═══════════════════════════════════════════╗
 ║║    System Name ORAC/2                              ║
 ╚║           City Phoenix_AZ                          ║
  ║  Operator Name Eugene_Glover                       ║
  ║   Phone Number 1-602-277-1334                      ║
  ║      Baud Rate 9600                                ║
  ║          Flags H16,CM,XA                           ║
  ║ .CFG  Password mailman                             ║
  ╚═│File_Request│ Human call  Poll_for_Mail  Quit ════╝

 Here AceComm has found the desired node information from the
 file 1_114.NOD.

 Notice the "Phone Number" field contains a long distance
 number.  The following "Dial Filter" statement" contained in
 "Point Mail Setup" menu is used to convert the phone number to a
 local number.
      1-602-
       (A)        (B)
 Explanation: Field (A) defines what to look for in phone numbers
      Filed (B) defines what to replace field (A) with.
      Here we left field (B) blank.  AceComm then
      replaces "1-602-" with nothing.

 Notice the "Password field. The following "Password"
 definition was made in "Point Mail Setup" menu.
      1:114/12 mailman

 The selector bar at the bottom of the above menu contains
 several choices. The first being "File Request". Selecting
 "File Request" produces the following screen.

 ╔═Input Window═════════════════════
 ║══════════════════════════════════
 ║FileName:  files
 ╚══════════════════════════════════

 AceComm is prompting for file names.  The example uses the file
 name "files".  Many systems will recognize "files" as a MAGIC
 file name, and send an "all files listing" for the system in
 response. Pressing <ENTER> alone when finished entering file
 names causes AceComm to begin dialing the target system.

     ╔══Record Number 1:114/12══════════════════════════════════
     ║     System Name   ORAC/2
     ║     Phone Number   1-602-277-1334
OK   ║     Line Control   9600L,8N1
     ║       Video Type
OK   ║ Control Flags      AutoMACRO,
     ║      Dial Prefix
     ║     Log on Script
     ║     Capture File
     ║         Password   mailman
     ║    Load KBD File
     ║═Trigger Sequence -- Responding MACRO STACK═══════════════
     ║
     ║═Last Connect  --   Total Connects ═══════════════════════
     ║ 0
     ║═Cycles     --      Dial String                       Last
     ║   0                ATEQ0X4DT277-1334
     ║ 00:03    00:03     58
     ╚═│Quit│ <SpaceBar>-ReCycle ┤<>v^├═════════════════════════
----------------------------------------------------------------
CONNECT 9600/ARQ
 Address 1:114/12 Using BinkleyTerm-OS/2 Ver. 2.56

Welcome to ORAC/2 - Home of Log/2 (Log for OS/2)
Press <escape> to enter BBS!
ORAC/2
Eugene Glover, Phoenix, AZ USA1-602-277-1334
BinkleyTerm, 9600, CM,XA,V32B,HST

  Outgoing  D:\ACE\mail\0072000C.REQ
 File Info  7 06/26/1993 11:55
0        7        0 CPS        00:00        ZEOF
 CPS                ZDATA
  Incoming  c:\fil\orac.lzh
 File Info  90401 06/24/1993 20:00
90401        289        1089 CPS        01:23        ZSendHexHdr
TIMEOUT

NO CARRIER

OK
----------------------------------------------------------------
AceComm uses it's text based display for the Point Mail protocol
displays.

AceComm  contains  internal Xmodem, Xmodem 1k, Ymodem, Ymodem 1k,
Ymodem G, Zmodem, and a Zmodem variant ZedZap (8k).

--Internal Batch Capable--
  AceComm's internal "Batch" capable protocols are capable of
  sending from a LISTFILE.  A LISTFILE is an ascii text file
  containing <CR> <LF> terminated filenames.  One filename per
  line.  Filenames may contain a full DRIVE:\PATH specifier.
  AceComm looks in the current directory for a filename
  "ACE.BCH".  When selecting any of the "Batch" capable internal
  sending units, AceComm will always look for "ACE.BCH", if the
  file exists, AceComm displays the following screen.

 ╓─────────────────╖      AceComm always prompts to send the
 ║ Found ACE.BCH   ║   from the LISTFILE "ACE.BCH", when the
 ║ Send contents?  ║   "ACE.BCH" file exists in the directory.
 ║(Y)es/(n)o?:    ║   Pressing <CR> defaults to (Y)es, (n)o
 ╙─────────────────╜   brings up the regular file selection
       menu.


 ╓───────────────────╖      If the (Y)es selection was selected,
 ║ ACE.BCH           ║   AceComm will, after the transfer,
 ║ Delete this file? ║   present the menu at left, prompting to
 ║(Y)es/(n)o?:      ║   delete the LISTFILE, or leave it exist.
 ╙───────────────────╜



The "Regular file selection" menu (below) allows "on the fly"
LISTFILE creation.  The "on the fly" LISTFILE is not named
"ACE.BCH", but a temporary unique filename is selected.  "On the
fly" LISTFILE is deleted after transfer without any prompt.

     ╓─Make Uploads List────────────────╖
     ║Batch Tag                        ║
     ║ Manual entry                     ║
     ║ Finished  /  ESC-key             ║
     ╙─ Select  Quit ───────────────────╜

Batch Tag
This selection brings up the "FileLister" menu.  This
menu allows tagging filenames to the LISTFILE.  PRM-data
DIR "DNLDS" is the default directory displayed by
"FileLister" when called by the "Sender Protocols" menu.

Manual entry
The  menu  below  is  presented  with the "Manual entry"
selection.

  ╓─Make Uploads List─────────────────╖
  ║ Batch Tag                         ║
  ║╓─Input Window───────────────────────────────────────────────
  ║║FileName:  c:\fil\
  ╙║─Input Window<ENTER> alone when done────────────────────────
   ╙────────────────────────────────────────────────────────────
  The "Manual entry" filename prompt pre pends the prompt space
  with any PATH found in PRM-data DNLDS field.


  "Batch Tag/ Manual entry" are recorded to a temporary unique
  LISTFILE as explained above.  Temporary unique LISTFILE is
  automatically deleted after use.


  - Single File
    AceComm's internal protocols that send 1 filename per
    invocation use the "Manual entry" window shown below.

  ╓─Input Window───────────────────────────────────────────────
  ║FileName:  c:\fil\
  ║─Input Window<ENTER> alone when done────────────────────────
  ╙────────────────────────────────────────────────────────────

--Externals--
  This selection brings up a menu listing up to five
  configurations for external protocol setup/selection.  This
  menu allows storing configurations for external protocols to be
  used.  The menu storage below functions the same as any MACRO
  stack assigned to a key press.  Here you have a menu where you
  may find it easier to to store specific upload protocol
  definitions.

 ╓─ External Protocols (UpLd) ──────────────────────────────────
 ║<RunProgram>BIMODEM %WK
 ║ <RunProgram>HSLINK %PF %WK
 ║ <RunProgram>MPT S @ACE.BCH %WK
 ║ <RunProgram>JMODEM S %PF %WK
 ║ <RunProgram>DSZ sz %PF
 ╙─ Select  Edit  Quit ─────────────────────────────────────────


-- Send Mail / File Attach--
  This selection allows the user to send files to EMSI capable
  mailer software.  The menu shown below prompts the user for a
  FIDONET style ZONE:NET/NODE number.

 ╓───────────────────────────────────────╖
 ║                                      ║
 ║ Format =>  ZONE:NET/NODE              ║
 ╙───────────────────────────────────────╜

  The number is required for naming a LISTFILE.  LISTFILE in the
  mode uses "MLF" file extension.  (Mail ListFile) AceComm allows
  normal Tag or manual entry when adding filenames to LISTFILE.
  Those who want to "File Attach" or are running under a HOST as
  a point mail system will use this option.  Point mail operators
  may upload their mail bundles with this "Send Mail" selection.
  AceComm requires a NODELIST or FBL output .NOD file when using
  "Send Mail/Attach".  AceComm uses the ZONE:NET/NODE number
  entered above for looking up system information about the HOST
  to be called.  AceComm is able to retrieve the phone number and
  system name from NODELIST/.NOD files.

  
The Telephone Directory Area lists binary .FON files in their
full ASCII representation.  The current loaded .FON file is
identified at the top of the menu.  Notice that the number of
records contained in the '1_114.FON' file is presented at the top
right.  .FON files are not fixed to any certain record size, and
can have records added or deleted, from here, in the Directory
list area.  Maximum record count for a FON file is 250 records
per FON file.  AceComm supports unlimited FON files, and provides
easy directory List/Grab function for changing FON files.

- Dial
  Dial the "highlighted" record.  The function continues dialing
  until:

     (a) a connection has been established

     (b)  USER ABORT.

- Edit
  Another menu contains the "highlighted" record's data is
  presented for editing, or just a closer view.  All changes are
  automatically save to disk.


- <SPACEBAR>-Que
  Mark the "highlighted" record for 'RedialQue'.

- Circular_Redial_Que
  Switch into The 'Que' Menu.  At least 1 record needs be marked
  "Queued" for AceComm to present this area.  From the 'Que'
  Menu, 'Dial' goes into single dial mode, and each record is
  dialed 1 time, followed by the next record until all records in
  the 'Que' have been dialed.  The 'Que' then revolves around to
  the first record and begins again.  When a connection has been
  established, the record is removed from the 'Que'.

╔═ Circular_Redial_Que D:\ACE\1_114.FON, 6 Records══════════════
║═      System Name            Phone Number     Line Control Vid
║14  Artemis Lair bbs         1-602-841-4474     9600,8N1    A
║ 15  Astroland                1-602-381-8708     9600,8N1    A
║ 16  Bob's Place BBS Node 1   1-602-497-2173     2400,8N1    A
║ 17  Bob's Place BBS Node 2   1-602-545-8745     9600,8N1    A
║ 18  Broadcaster's BBS        1-602-872-9148     9600,8N1    A
║ 19  CADE BBS                 1-602-931-3468     2400,8N1    A
║  Dial  Edit  <SPACEBAR>-Zap  Telephone_Directory
╚═ Add_record  Remove_record  UnMark_All  Import  Paint  Quit ┤<

-Fon_files
  List PRM-data directory .FON, allow selection of new .FON file

- Add_record
  Function appends a new record to the current loaded .FON file,
  and immediately brings up the 'Edit' Menu.  The new record is
  automatically saved.

- Remove_record
  The "highlighted" record is removed  from  the  current  loaded
  .FON file.  No hole is left, the .FON file is reduced a 'record
  size' in bytes.

- UnMark_All
  Clear TAG bit from all records in the current FON file.

- Import
  Convert another software's FON type file to AceComm FON file.
  ╔═Covert to AceComm FON format═╗
  ║ BOYAN 5                     ║
  ║  Qmodem 4                    ║
  ║  Qmodem 5                    ║
  ║  Procomm 2.43                ║
  ║  PcPlus 1                    ║
  ║  PcPlus 2                    ║
  ║  Telemate 3.01               ║
  ║  Telemate 4.11               ║
  ║  TELIX 3.15 - 3.21           ║
  ║                              ║
  ╚═══ Select  Quit ┤<>v^├═══════╝

- Paint
  Customize the current menu only.  All changes are save
  automatically.

- Quit to Terminal Area. (ESC-key)


.FON files

AceComm uses a binary .FON file for storing it's telephone
directory records.  Each record contains data specific to the
system. FON files must be edited inside AceComm, using The Edit
menu.


- System Name            AceComm Software Support
  The name defined here, is presented onto the revolving status
  line (right side of status line) when "on line".

- Phone Number           1-602-846-2940
  This  phone  number, although long distance, can be modified by
  AceComm when dialing, with use of "Dial" statements in the
  Point Mail Menu.

  Example: lets say we are local Phoenix, where our area code is
   602, we have an entire phone directory of long
   distance numbers.  The following dial statement
   defined inside "Point Mail Setup" will cause AceComm
   to translate all of the long distance numbers to local
   numbers.

   Dial 1-602-

   AceComm will see this definition and translate it into
   anything following the definition.  In this case, we
   did not put anything after the "1-602-", so AceComm
   will strip "1-602-" from all phone numbers that
   contain "1-602-" as part of the number.  This is valid
   for all phone numbers that are processed thru the
   AceComm Dialer Menu.  Mailer mode, File Requests which
   get their phone numbers from either a FIDO NODELIST,
   of FBL output .NOD file do use the Dialer Menu and do
   receive number translation from "Dial" statements.

- Line Control           2400L,8N1
  Most remote HOSTS will be set up using 8 data bits, No parity,
  and 1 stop bit.  Compuserve uses 7 data bits, Even parity, and
  1 stop bit.  AceComm will configure the UART to assemble the in
  coming bit stream into characters, based on the configuration
  defined here.  Baud rate means nothing when LOCKBAUD is set, as
  is with the "L" appended to baud in this example.  Other wise,
  when LOCKBAUD is not set, AceComm will set the UART up to the
  Fon.Record baud rate.

  Note: When LOCKBAUD is not set, AceComm is also capable of
resetting the baud rate to a connect string.  If you dial
out at 2400, and connect at 9600, and 9600 is detected in
the the connect string, AceComm will automatically set
the baud to 9600.  If LOCKBAUD is set, AceComm leaves
baud alone.

- Terminal Emulation     Av/An
  This option will present the Terminal emulations menu, you may
  select the video ,type you want associated with this record.
  "Av/An means AVATAR and ANSI video emulation.

- Control Flags          AutoMACRO/SCRIPT,DTAG,CAPTURE

  "SCRIPT"  when  set,
  AceComm will attempt to load and run the filename defined next
  to "AutoLogOn Script".  If a script file is not found, AceComm
  ignores the error and continues normal operation.

  "AutoMACRO"  when  set,
  AceComm will enable the defined Auto Log on Trigger Sequence
  and corresponding MACRO stack.

  To turn Auto Logons "OFF", set SCRIPT bit, and delete the
  Fon.Record.Script_file field, or select a NULL AutoLM
  trigger/MACRO.

  "DTAG"  when  set,
  AceComm will tag un-successful dial attempts (busy, etc.) to
  the Que Dialer.  An "*" character appears to the left of a
  Fon.Record's display line, when it is either Q tagged or, D
  tagged.  When this flag is not set, the only other way to Q tag
  a record is by manually selecting the menu option
  "<SPACEBAR>-Que" from the fon list display.

 "CAPTURE"
 When this flag is selected, a capture file is opened upon
 Dial/Connect.  Any previously open capture file is first closed.

- Dialing Prefix
  The Fon.Record dial prefix overrides The PRM-data default
  prefix.  If this field is null (blank), AceComm uses the
  PRM-data default dial prefix.

- AutoLogOn Script       ACE_S.SCR
  When SCRIPT flag is set, for the current Fon.Record, AceComm
  will use this filename, opening it as a SCRIPT file, and run
  the contents.  This action takes place upon successful
  Dial/Connect.  If the filename does not exist, AceComm simply
  goes about it's business, and you will log on normally.
  AceComm will look for the SCRIPT filename in PRM-data DIR .SCR
  path.

- Capture File           ACE_S.CAP
  Default filename presented to user when opening a "capture data
  to file" file.

- Password               my/password
  See also: Expandable MACRO Parameters <SendStr> [FON_PASSWORD]
  would replace "[FON_PASSWORD]" with "my/password" for this
  example.  You may define the Fon.Record PASSWORD field to any
  character combination, the field maximum length is 19
  characters.

- Custom .KBD File       MY.KBD
  KeyBoard File, AceComm will first remember what the current KBD
  filename is, load the Fon.Record's custom KBD file, if defined,
  and finally restore the original KBD file after session
  disconnect.  Say What?

  You are about to log onto Compuserve.  You have CIS.KBD file
  defined for the Fon.Record.  When dial/connect is detected,
  AceComm will load the contents of CIS.KBD, overlaying your
  current keyboard MACRO assignments.  When you log off of
  Compuserve, and AceComm detects the carrier drop (no DCD),
  AceComm will load back the original keyboard file, overlaying
  your custom CIS.KBD.

  You will need to distinguish KBD files from KTS files.  Where a
  KBD file overlays the keyboard MACRO assignments.  The KTS file
  defines the ultimate sequence that will be sent to the modem
  for a given key-press.  Keys assigned a MACRO, are processed as
  MACRO functions.

  Keys not assigned a MACRO(s) will be sent to the modem, and are
  candidates for KTS.

  Keys with extended codes, are sent as they would be seen in
  DoorWay mode.  Normal keys (a-z,A-Z,1-0,CTRL A-CTRL Z, etc.)
  are sent in their normal lower ascii representation (as you
  would expect).  Now, any of these key-presses that have been
  defined inside the KTS file, are translated into their defined
  sequence.  AceComm & Utilities provides ASCII examples for
  compiling KTS files, as well as KTS.EXE the custom Keyboard
  Sequence Translation (Tm) compiler.

- Auto Log on Trigger Sequence/MACRO Stack
  Each Fon.Record can be assigned to one of the Auto Log on
  definitions available from a menu when selecting this option.
  AceComm will respond to a trigger sequence by processing the
  MACRO stack. Log on trigger sequence scanning is available
  immediately after connect, and until the sequence has been
  found. When a log on sequence has been processed, AceComm
  stops scanning for the log on sequence.

 ╔═D:\ACE═══════════════════════════════╗
 ║ 1_114.FON    26368   06/27/93 07:25 ║
 ║  ACE.ASM      8269    06/26/93 18:00 ║
 ║  ACE.CTL      13589   06/25/93 08:04 ║
 ║  ACE.EXE      196102  06/27/93 07:24 ║
 ║  ACE.FON      1600    06/27/93 04:13 ║
 ║  ACE.HLP      44572   06/27/93 07:09 ║
 ║  ACE.LOG      3694    06/27/93 07:29 ║
 ...
 ║  ACTL.ASM     101998  06/25/93 14:22 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝

- Utility
  This selection brings up a sub-menu of pre-defined executable.
  AceComm contains several sub-menus for this purpose.  Sub-menu
  selected is determined by the "highlighted" files's extension.
  The %FN symbol is documented in MACRO.DOC.  %FN is an
  Expandable MACRO Function.  %FN argument to a MACRO from
  anywhere inside the "File Lister" menus is replaced with FULL
  PATH NAME for the current high lighted filename.

 ╔═C:\DOC═══════════════════════════════╗
 ║  A.SNA        1242    06/27/93 07:53 ║
 ║  ACE.BAK      117893  06/26/93 12:25 ║
 ║  ACE.CHA      2706    06/27/93 07:46 ║
 ║╔═%FN = C:\DOC\ACE.DOC══════════════════════════════════
 ║ ║ <RunProgram> BB %FN
 ║ ║<RunProgram> LIST %FN
 ║ ║ <RunProgram> QEDIT %FN
 ║ ║ <RunProgram> GREP %PF %FN %PF
 ║ ║ <RunProgram> PATCH %FN
 ║ ╚═ Select  Edit  Quit ┤<>v^├════════════════════════════
 ║  COVER        213     06/25/93 16:22 ║
 ║  CREDIT.CRD   2918    06/25/93 15:30 ║
 ...
 ║  FILE_ID.DIZ  392     06/26/93 13:14 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝


- New_Dir
  Allows changing directories.  AceComm changes directories right
  along with the display.  When you use AceComm's  "Utils"  Menu,
  work is done in the currently listed directory unless otherwise
  redirected   via   MACRO   arguments   or  overriding  external
  executable configurations.

  Notes: AceComm always returns to the starting  directory  after
 leaving the FileLister Area.
    ╔═D:\ACE═══════════════╗
 ╔═D:\ACE═══════════║D:\ACE              ║
 ║ 1_114.FON    263║ ..                  ║
 ║  ACE.ASM      826║ CAP                 ║
 ║  ACE.CTL      135║ CVTFON              ║
 ║  ACE.EXE      196║ FILES               ║
 ║  ACE.FON      160║ FON                 ║
 ║  ACE.HLP      445║ KTS                 ║
 ║  ACE.LOG      369║ MAIL                ║
 ║  ACE.MAP      920║ SCR                 ║
 ║  ACE.OBJ      271║ SND                 ║
 ║  ACE.PRM      378║ XTRA                ║
 ║  ACEBOX.INC   345║ ZEN                 ║
 ║  ACEM         253║ F                   ║
 ║  ACEORDER.FRM 588╚═ Select  Quit ┤<>v^├═╝
 ║  ACET.SCR     809     05/17/93 21:33 ║
 ...
 ║  ACTL.ASM     101998  06/25/93 14:22 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit   Help ┤<>v^├═════╝


- Change Drive
  Allows listing another drive.
 ╔═D:\ACE═══════════╔══════════════════════╗
 ║ 1_114.FON    263║A                    ║
 ║  ACE.ASM      826║ B                    ║
 ║  ACE.CTL      135║ C                    ║
 ║  ACE.EXE      196║ D                    ║
 ║  ACE.FON      160║ E                    ║
 ║  ACE.HLP      445╚═ Select  Quit ┤<>v^├═╝
 ║  ACE.LOG      3694    06/27/93 07:29 ║
 ...
 ║  ACTL.ASM     101998  06/25/93 14:22 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝


- Tagged files
  Tagged files are stored in the file "ACE.BCH" when tagged from
  inside the <FileLister_> MACRO.  When tagged from any of
  AceComm's internal protocol sending units, tagged filenames are
  stored into a temporary file.  The temporary file is deleted
  after each use.  ACE.BCH files are not deleted, but instead
  stored ready.

  AceComm will look for ACE.BCH when any internal batch capable
  protocols are selected.  If found, AceComm will ask the user is
  sending the contents of ACE.BCH is desired, if (Y)es, AceComm
  will attempt to send all filenames listed in the ACE.BCH file,
  if (n)o, AceComm will present the the File Input' menu.
 ╔═D:\ACE═══════════════════════════════╗╔═ACE.BCH══════════════
 ║  1_114.FON    26368   06/27/93 07:25 ║║D:\ACE\1_114.FON
 ║ ACE.ASM      8269    06/26/93 18:00 ║║
 ║  ACE.CTL      13589   06/25/93 08:04 ║║
 ║  ACE.EXE      196102  06/27/93 07:24 ║║
 ║  ACE.FON      1600    06/27/93 04:13 ║║
 ║  ACE.HLP      44572   06/27/93 07:09 ║║
 ║  ACE_MAIL.CFG 430     06/22/93 14:23 ║║
 ...
 ║  ACTL         591     06/22/93 14:08 ║║
 ║  ACTL.ASM     101998  06/25/93 14:22 ║║
 ║  Utility  New_Dir  Change_Drive      ║╚══════════════════════
 ╚═│Tag│ Delete  Quit  Help ┤<>v^├══════╝


- Delete
  Delete option presents a full path spec for the high lighted
  filename, prompting confirmation before deletion.
 ╔═D:\ACE═══════════════════════════════╗
 ║  1_114.FON    26368   06/27/93 07:25 ║
 ║╔═══════════════════╗ 06/27/93 07:31 ║
 ║ ║ D:\ACE\A.SNA      ║ 06/26/93 18:00 ║
 ║ ║ Delete this file? ║ 06/27/93 07:31 ║
 ║ ║(Y)es/(n)o?:      ║ 06/25/93 08:04 ║
 ║ ╚═══════════════════╝ 06/27/93 07:24 ║
 ║  ACE.FON      1600    06/27/93 04:13 ║
 ║  ACE.HLP      44572   06/27/93 07:09 ║
 ║  ACE_DEF.KBD  11120   06/27/93 07:29 ║
 ...
 ║  ACE_MAIL.CFG 430     06/22/93 14:23 ║
 ║  Utility  New_Dir  Change_Drive      ║
 ╚═ Tag  Delete  Quit  Help ┤<>v^├══════╝


EMSI handshake data
   The following data is presented to the remote mail system
   during EMSI handshaking.
   Address
   Sys Name AceComm Support
   City Phoenix, AZ
   Operator Michael Phelps
   Sys Phone (602) 846-2940
   Baud 14.4
   Flags v32b

   Password  --  Pre arranged between two systems.
   The following example will cause AceComm to fill in the EMSI
   data field for "password" with 'mailman' when the target
   system's address is 1:114/12.
  Password 1:114/12 mailman

   Dial filter  --  AceComm will use Dial statements to modify
   phone numbers. Dial filter statements are used when dialing
   from inside of AceComm's phone directory, and or with mail
   functions.
   A long distance BBS directory list can be used without
   editing phone numbers.

   The following dial statement filter "1-602-" from all phone
   numbers the  string is found in.
  Dial filter 1-602-

   The following dial statement converts "1-602-451" found in
   phone numbers to "1-451".
  Dial filter 1-602-451 1-451

   Dial statements are required when using point mail
   functions, because NODELIST phone numbers contain area
   codes. AceComm uses dial statements to know how to modify
   phone numbers.


  Point mail functions look in the PRM-data directory "NODELIST"
  for systems directories.  Point mail functions require either
  of two types systems directories.

  Systems directory type (FIDO  NODELIST)
     FIDO NODELIST is a systems directory that most EMSI capable
     HOST systems use.  AceComm can use a FIDO NODELIST.  To use
     the FIDO NODELIST, you must first compile an INDEX file.
     AceComm uses NLIST.IDX.  NLIST.IDX contains a quick look up
     table for Zone:Net/Nodes in the FIDO NODELIST.  The AceComm
     package provides IDX.EXE as a utility to create the
     NLIST.IDX file.  NLIST.IDX and the NODELIST are to be found
     inside of the PRM-data directory "NODELIST".

  Systems directory type (FBL.EXE output .NOD file)
     .NOD file is a NET extraction from the FIDO NODELIST.
     FBL.EXE (provided) is capable of creating this file.  .NOD
     files contain a listing for a single NET.  .NOD files are
     very small and may be preferable for point mail use where
     calling 1 or a few pre know NETS is intended.  .NOD files
     are to be found inside of the PRM-data directory "NODELIST".


Support for a pointer device has been implemented into AceComm
using the Microsoft Mouse Driver functions. Your Microsoft
compatible mouse should work with AceComm.

-- Mouse in Terminal Area --

o Pressing the left mouse button sends <CR>

o Pressing right mouse button sends the character the mouse
  cursor is highlighting.


From Terminal Area, a one line mouse menu is presented on the top
row of the screen.  This menu presents several of the more
commonly used MACRO functions otherwise available from the
Terminal Area with a key press.

Placing the mouse cursor over a menu choice and pressing the left
button selects the menu item.

The menu can be toggled off from the PRM-data Terminal Options
menu.

The mouse can be used for Character I/O with the HOST.  The left
button sends <CR> character.  The right button sends the current
highlighted character.


-- Mouse in Menu Areas --

o Pressing the left button selects an item.

o Pressing the right button is the same as <ESC> or Quit

   Horizontal and vertical sensitivity can be adjusted from
   inside the PRM-data general controls menu.

   The mouse detection can be toggled "OFF" from inside the
   PRM-data General Controls menu.
   Turning "OFF" mouse detection completely disables AceComm
   from any mouse function related use, including Terminal Area
   mouse menu.

